Memory system and operation method for the same

ABSTRACT

A memory system includes a memory device including plural memory blocks, each including plural pages storing data, and a controller suitable for loading data from first memory blocks among the plural memory blocks to perform command operations corresponding to plural commands and securing second memory blocks among the plural memory blocks to store data updated by the command operations. The controller can exclude the first memory blocks from the second memory blocks.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority under 35 U.S.C. § 119(a) to Korean Patent Application No. 10-2018-0091321, filed on Aug. 6, 2018, the entire disclosures of each of which are incorporated herein by reference.

TECHNICAL FIELD

Exemplary embodiments of the invention relate to a memory system, and more particularly, to an apparatus and a method for controlling operations to process data with a non-volatile memory device.

BACKGROUND

Recently, a paradigm for a computer environment has shifted into ubiquitous computing, which enables a computer system to be accessed anytime and everywhere. The use of portable electronic devices such as mobile phones, digital cameras, notebook computers and the like is rapidly increasing. Such portable electronic devices typically use or include a memory system that uses or embeds at least one memory device, i.e., a data storage device. The data storage device can be used as a main storage device or an auxiliary storage device of a portable electronic device.

Unlike a hard disk, a data storage device using a nonvolatile semiconductor memory device is advantageous in that it has excellent stability and durability because it has no mechanical driving part (e.g., a mechanical arm), and has high data access speed and low power consumption. As an example of a memory system having such advantages, a data storage device includes a USB (Universal Serial Bus) memory device, a memory card having various interfaces, a solid state drive (SSD) or the like.

BRIEF DESCRIPTION OF THE DRAWINGS

The description herein makes reference to the accompanying drawings wherein like reference numerals refer to like parts throughout the several views, and wherein:

FIG. 1 is a block diagram illustrating an example of a memory system including plural memory blocks in accordance with an embodiment of the disclosure;

FIG. 2 is a block diagram illustrating an example of a data processing system including a memory system in accordance with an embodiment of the disclosure;

FIG. 3 is a block diagram illustrating an example of a memory system in accordance with an embodiment of the disclosure;

FIGS. 4 and 5 are diagrams illustrating an example in which a memory system in accordance with an embodiment of the disclosure performs a plurality of command operations corresponding to a plurality of commands;

FIG. 6 is a block diagram illustrating a memory system vin accordance with an embodiment of the disclosure;

FIGS. 7 to 9 illustrates different examples of a method for generating a free block list;

FIG. 10 describes an operation method for a memory system in accordance with an embodiment of the disclosure; and

FIGS. 11 to 19 are diagrams schematically illustrating other examples of data processing systems including a memory system in accordance with an embodiment of the disclosure.

DETAILED DESCRIPTION

Various examples of the disclosure are described below in more detail with reference to the accompanying drawings. The disclosure may be embodied in different other embodiments, forms and variations thereof and should not be construed as being limited to the embodiments set forth herein. Rather, the described embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the disclosure to those skilled in the art to which this invention pertains. Throughout the disclosure, like reference numerals refer to like parts throughout the various figures and examples of the disclosure. It is noted that reference to “an embodiment” does not necessarily mean only one embodiment, and different references to “an embodiment” are not necessarily to the same embodiment(s).

It will be understood that, although the terms “first”, “second”, “third”, and so on may be used herein to describe various elements, these elements are not limited by these terms. These terms are used to distinguish one element from another element. Thus, a first element described below could also be termed as a second or third element without departing from the spirit and scope of the invention.

The drawings are not necessarily to scale and, in some instances, proportions may have been exaggerated in order to clearly illustrate features of the embodiments. When an element is referred to as being connected or coupled to another element, it should be understood that the former can be directly connected or coupled to the latter, or electrically connected or coupled to the latter via an intervening element therebetween.

It will be further understood that when an element is referred to as being “connected to”, or “coupled to” another element, it may be directly on, connected to, or coupled to the other element, or one or more intervening elements may be present. In addition, it will also be understood that when an element is referred to as being “between” two elements, it may be the only element between the two elements, or one or more intervening elements may also be present.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

As used herein, singular forms are intended to include the plural forms and vice versa, unless the context clearly indicates otherwise.

It will be further understood that the terms “comprises,” “comprising,” “includes,” and “including” when used in this specification, specify the presence of the stated elements and do not preclude the presence or addition of one or more other elements. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

Unless otherwise defined, all terms including technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs in view of the present disclosure. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the disclosure and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the invention. The invention may be practiced without some or all of these specific details. In other instances, well-known process structures and/or processes have not been described in detail in order not to unnecessarily obscure the invention.

It is also noted, that in some instances, as would be apparent to those skilled in the relevant art, a feature or element described in connection with one embodiment may be used singly or in combination with other features or elements of another embodiment, unless otherwise specifically indicated.

Embodiments of the disclosure can provide a memory system, a data processing system, and an operation process or a method, which can quickly and reliably process data into a memory device by reducing operational complexity and performance degradation of the memory system and enhancing usage efficiency of the memory device.

Embodiments of the disclosure can provide a memory system and a method of operating a memory system capable of managing a plurality of memory blocks included in a memory device as a free block list for enhancing an efficiency.

In addition, in an embodiment of the disclosure, it is possible to provide an apparatus and a method that can reduce a risk that data may be lost due to an error or an operation fail, when free blocks for operations to program or move voluminous data are secured in advance, or information capable of restricting usable blocks in free blocks is used.

In an embodiment, a memory system can include a memory device including plural memory blocks, each including plural pages storing data, and a controller suitable for loading data from first memory blocks among the plural memory blocks to perform command operations corresponding to plural commands, and securing second memory blocks among the plural memory blocks to store data updated by the command operations. Herein, the controller can exclude the first memory blocks from the second memory blocks.

By the way of example but not limitation, the controller can exclude the first memory blocks from the second memory blocks even if the first memory blocks become free blocks during the command operation. After the command operations are completed, the controller can include the first memory blocks, which become the free blocks during the command operations, in the second memory blocks for another operation.

The controller can generate, and manage, a free block list having a structure of bitmap including bit information indicating whether each the first memory blocks and the second memory blocks are available. The first memory blocks may become a free block during the command operation. For example, first bit information, corresponding to the first memory blocks in which the command operations are performed, in the free block list is a first value, while second bit information corresponding to the second memory blocks in the free block list is a second value which is the opposite of the first value.

In an embodiment, the controller can generate a list regarding the second memory blocks before the command operations are begun. The list may be not updated nor changed while the command operations are performed.

In an example, while the command operations are performed, the controller can update a list when at least one of memory blocks other than the first memory blocks is changed to the second memory blocks.

By the way of example but not limitation, the controller can update a list regarding newly added second memory blocks, regardless of the command operations. The list can include bit information each indicating whether each of the second memory blocks is available.

After storing information regarding the command operations to the second memory blocks before an occurrence of sudden power off (SPO), the controller can load the information stored in the second memory blocks to perform the command operations when a power is supplied.

The command operations can include a foreground operation and a background operation performed in the memory device. For example, the foreground operation and the background operation may include at least one of a data program operation, a data erase operation and a data read operation.

In another embodiment, a memory system can include a memory device including a plurality of memory blocks, each including a plurality of pages in which data is stored and a controller suitable for loading a map data and a user data for an operation, corresponding to a command, on first memory blocks in the plurality of memory blocks, and determining second memory blocks which store updated map data and updated user data through the operation corresponding to the command. Even if at least one of the first memory blocks becomes a free block, the controller can exclude the at least one first memory block from the second memory blocks until the updated map data and the updated user data are stored in the second memory blocks.

By the way of example but not limitation, the controller can generate a list regarding the second memory blocks before the command operations are begun. The list may be not updated nor changed while the command operations are performed.

In an example, while the command operations are performed, the controller may update a list when at least one of memory blocks other than the first memory blocks is changed to the second memory blocks.

The controller can update a list regarding newly added second memory blocks regardless of the command operations. Herein, the list can include plural bit information, each indicating whether each of the second memory blocks is available.

The command operations can include a foreground operation and a background operation performed in the memory device. For example, the foreground operation or the background operation can include a data program operation, a data erase operation or a data read operation.

In another embodiment, a method for operating a memory system can include receiving plural commands, entered from a host and associated with a memory device including plural memory blocks, each including plural pages storing data, loading data from first memory blocks among the plural memory blocks to perform command operations corresponding to the plural commands, and securing second memory blocks among the plural memory blocks to store data updated through the command operations. Even if at least one of the first memory blocks becomes a free block, the controller can exclude the at least one first memory block from the second memory blocks until the updated data is stored in the second memory blocks.

The securing the second memory blocks can include generating a list in which information of the second memory blocks are arranged and sorted.

The list can include bit information, each corresponding to each memory block and indicating whether each of the first memory blocks, which become a free block during the command operations, and the second memory blocks are available.

The controller can update the list when a new free block is generated, regardless the command operations.

The list can be generated before the command operations are begun. The list may be not updated nor changed while the command operations are performed.

The securing of the second memory blocks can further include updating a list when at least one of memory blocks other than the first memory blocks is changed to the second memory blocks while the command operations are performed.

In another embodiment, a memory system can include a memory device including one or more blocks-in-use, one or more blocks-not-in-use and one or more first free blocks; and a control unit suitable for: controlling the memory device to performing an operation of moving data from one or more among the blocks-in-use and blocks-not-in-use into the first free blocks; and controlling, even when the block-in-use becomes a second free block during the operation, the memory device to keep the second free block during the operation. The blocks-in-use are memory blocks storing data to be moved through the operation. The blocks-not-in-use are memory blocks other than the blocks-in-use and the free blocks.

Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanied drawings.

In FIG. 1, an example of a memory system 110 in accordance with an embodiment of the disclosure is described. A memory system 110 can include a controller 130 and a memory device 150. The memory system 110 may be engaged with another device, e.g., a computing device.

Referring to FIG. 1, there are the controller 130 and the memory device 150 in the memory system 110. The memory device 150 may include a non-volatile memory. The controller 130 may program data, externally transmitted, into the memory device 150 or read data, externally requested, from the memory device 150.

The memory device 150 including a plurality of nonvolatile memory cells does not support overwriting. The controller 130 may store changed or updated version of data, stored at a particular location, in another location within the memory device 150.

Although not shown, the controller 130 may perform various operations to enhance or improve operation reliability of the memory system 110. For example, wear leveling can be one of the various operations. In a memory system including a non-volatile memory which can erase and write data, such as a solid state drives (SSD), a USB flash drive, a phase-change memory, the wear leveling is considered a technique for extending a life time of the memory system, e.g., improving durability. It is possible to provide a wear equalization mechanism that recognizes the extent, to which a cell storing data in such a memory system is worn-out, to provide various levels of life time extension. Such a wear equalization mechanism can be applied to an operation such as garbage collection (GC) releasing an unnecessary area including invalid or discarded data to be used (programmed) within a memory area dynamically allocated for a following program operation.

Referring to FIG. 1, the memory system 110 can move a large amount of data during wear leveling or garbage collection. The memory device 150 in the memory system 110 may include a first memory block 40_1, which is a block in which data is stored, and a second memory block 40_2, which is a free block in which no data is stored (e.g., erased to be programmed by new data). For example, the controller 130 reads the data stored in the first memory block 40_1 and loads the read data into the memory 144 in the controller 130 and then stores the loaded data in the second memory block 40_2. In the process of transferring a large amount of data from the first memory block 40_1 to the second memory block 40_2, the controller 130 should load metadata regarding the data to be transferred. The metadata can be updated and stored in the memory device 150.

When the metadata of the transferred or moved data is updated after the large amount of data is normally transferred, there might be no problem in the operation requested from a host 102 (see, FIG. 2) to exchange data with the memory system 110. However, when the large amount of data does not move normally or the metadata about the transferred or moved data may not be normally updated, it might be difficult for the memory system 110 to transmit data requested by the host 102 because the memory system 110 may not find the requested data in the memory device 150.

Since it takes a certain time to move a large amount of data, an unexpected problem or issue may occur within a memory system in a process of moving a large amount of data so that the process of moving a large amount of data may not be normally completed. For example, a power issue may arise in the process of moving a large amount of data. A large amount of data may not be transferred to the second memory block 40_2 due to internal or external factors such as sudden power-off (SPO) in which the powersupply is interrupted. When the power supply is resumed after being interrupted, the controller 130 can re-execute the operation of transferring or moving a large amount of data that was performed before the power supply was interrupted. In addition, problems may occur due to internal or external factors in the process of updating the metadata. In this case, when the internal or external factor disappears, the controller 130 needs to recover the metadata so that the metadata is normally updated.

The memory system 110 can correct an error through a data recovery process performed by the controller 130 even when the operation of moving a large amount of data is abnormally terminated. However, a data recovery operation may generally scan all the data areas in the memory system 110 to recognize a status of how far the operation progressed in the memory system 110 (e.g., which data is completely transferred or not). In this case, a considerable time may be required for the data recovery operation so that the performance and reliability of the memory system 110 may be deteriorated.

When programming or transferring a large amount of data, the controller 130 can generate a free block list 37 for determining whether the first memory block 40_1 and the second memory block 40_2 can be used as a free block according to a current data storage state. When a large amount of data delivered from an external device is written or programmed into the memory device 150 or when a large amount of data is transferred or moved for wear leveling or garbage collection or the like, the controller 130 can program the large-capacity data to the second memory block 40_2 without difficulty if a sufficient amount of free memory blocks are secured. However, when the second memory block 40_2 has insufficient size for the large-capacity data, the controller 130 could perform garbage collection to make at least one new free memory block. The controller 130 collects valid data in some of the plurality of first memory blocks (i.e., data blocks) 40_1 and transfers the valid data to the second memory block (i.e., free blocks) 40_2. Some of the plurality of first memory blocks 40_1 from which the valid data is moved or transferred can be erased and be set as free blocks for programming voluminous data.

When data is moved from the first memory block 40_1 to the second memory block 40_2, the first memory block 40_1, which no longer has valid data, can be classified as a free block and the second memory block 40_2 in which the valid data is moved can be classified as a data block. When a power is supplied or resumed after the power not supplied or interrupted such as sudden power-off during the s process of transferring or programming a voluminous data, the controller 130 may determine that the first memory block 40_1 which has no longer valid data became a free block. However, it is assumed that the operation of moving a large amount of data is terminated abnormally. When a data block previously storing the moved data is considered a free block without confirming whether the data has been completely moved or whether the map data corresponding to the moved data has been updated, there is a possibility that at least some of the large amount of data would be lost.

Therefore, in order to avoid such a problem, the first memory block 40_1 in which data is stored may have a first value ‘0’ and the second memory block 40_2 having no data may have a second value ‘1’ in the free block list. Accordingly, even when the operation of moving a large amount of data is abnormally terminated, the controller 130 can recognize which block the moved data was previously stored, exclude the recognized blocks from free blocks for storing voluminous data, and avoid the possibility of losing at least a part of the data.

In FIG. 2, a data processing system 100 in accordance with an embodiment of the disclosure is described. Referring to FIG. 2, the data processing system 100 may include a host 102 engaged or interlocked with a memory system 110.

The host 102 may include, for example, a portable electronic device such as a mobile phone, an MP3 player and a laptop computer or an electronic device such as a desktop computer, a game player, a television (TV), a projector and the like.

The host 102 also includes at least one operating system (OS), which can generally manage, and control, functions and operations performed in the host 102. The OS can provide interoperability between the host 102 engaged with the memory system 110, and the user who is using the memory system 110. The OS may support functions and operations corresponding to the user's requests. By way of example but not limitation, the OS can be classified into a general operating system and a mobile operating system according to mobility of the host 102. The general operating system may be split into a personal operating system and an enterprise operating system according to system requirements or the user's environment. The personal operating system, including Windows and Chrome, may be subject to support services for general purposes. But the enterprise operating systems can be specialized for securing and supporting high performance, including Windows servers, Linux, Unix and the like. Further, the mobile operating system may include an Android, an 10S, a Windows mobile and the like. The mobile operating system may be subject to support services or functions for mobility (e.g., a power saving function). The host 102 may include a plurality of operating systems. The host 102 may execute multiple operating systems interlocked with the memory system 110, corresponding to the user's request. The host 102 may transmit a plurality of commands corresponding to user's requests into the memory system 110, thereby performing operations corresponding to commands within the memory system 110. Handling plural commands in the memory system 110 is described later, referring to FIGS. 4 and 5.

The memory system 110 may operate or perform a specific function or operation in response to a request from the host 102 and, particularly, may store data to be accessed by the host 102. The memory system 110 may be used as a main memory system or an auxiliary memory system of the host 102. The memory system 110 may be implemented with any one of various types of storage devices, which may be electrically coupled with the host 102, according to a protocol of a host interface. Non-limiting examples of suitable storage devices include a solid state drive (SSD), a multimedia card (MMC), an embedded MMC (eMMC), a reduced size MMC (RS-MMC), a micro-MMC, a secure digital (SD) card, a mini-SD, a micro-SD, a universal serial bus (USB) storage device, a universal flash storage (UFS) device, a compact flash (CF) card, a smart media (SM) card, a memory stick, and the like.

The storage devices for the memory system 110 may be implemented with a volatile memory device, for example, a dynamic random access memory (DRAM) and a static RAM (SRAM), and/or a nonvolatile memory device such as a read only memory (ROM), a mask ROM (MROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a ferroelectric RAM (FRAM), a phase-change RAM (PRAM), a magneto-resistive RAM (MRAM), a resistive RAM (RRAM or ReRAM) and a flash memory.

The memory system 110 may include a controller 130 and a memory device 150. The memory device 150 may store data to be accessed by the host 102. The controller 130 may control storage of data in the memory device 150.

The controller 130 and the memory device 150 may be integrated into a single semiconductor device, which may be included in the various types of memory systems as exemplified above.

By the way of example but not limitation, the controller 130 and the memory device 150 may be integrated into a single semiconductor device. The controller 130 and memory device 150 configuring an SSD may be integrated into a single semiconductor device, for improving an operation speed. When the memory system 110 is used as an SSD, the operating speed of the host 102 connected to the memory system 110 can be improved more than that of the host 102 implemented with a hard disk. In addition, the controller 130 and the memory device 150 integrated into one semiconductor device may form a memory card. For example, a PC card (PCMCIA), a compact flash card (CF), a memory card such as a smart media card (SM, SMC), a memory sticks, a multimedia card (MMC, RS-MMC, MMCmicro), a SD card (SD, miniSD, microSD, SDHC), a universal flash memory and the like.

The memory system 110 may be configured as a part of, for example, a computer, an ultra-mobile PC (UMPC), a workstation, a net-book, a personal digital assistant (PDA), a portable computer, a web tablet, a tablet computer, a wireless phone, a mobile phone, a smart phone, an e-book, a portable multimedia player (PMP), a portable game player, a navigation system, a black box, a digital camera, a digital multimedia broadcasting (DMB) player, a 3-dimensional (3D) television, a smart television, a digital audio recorder, a digital audio player, a digital picture recorder, a digital picture player, a digital video recorder, a digital video player, a storage configuring a data center, a device capable of transmitting and receiving information under a wireless environment, one of various electronic devices configuring a home network, one of various electronic devices configuring a computer network, one of various electronic devices configuring a telematics network, a radio frequency identification (RFID) device, or one of various components configuring a computing system.

The memory device 150 may be a nonvolatile memory device and may retain data stored therein even while an electrical power is not supplied. The memory device 150 may store data provided from the host 102 through a write operation, while providing data stored therein to the host 102 through a read operation. The memory device 150 may include a plurality of memory blocks 152, 154, 156. Each of the memory blocks 152, 154, 156 may include a plurality of pages. Each of the plurality of pages may include a plurality of memory cells to which a plurality of word lines (WL) are electrically coupled. The memory device 150 also includes a plurality of memory dies each of which includes a plurality of planes, each of which includes a plurality of memory blocks 152, 154, 156. In addition, the memory device 150 may be a non-volatile memory device, for example a flash memory, wherein the flash memory may be a three-dimensional stack structure.

The controller 130 may control overall operations of the memory device 150, such as read, write, program and erase operations. For example, the controller 130 may control the memory device 150 in response to a request from the host 102. The controller 130 may provide the data, read from the memory device 150, with the host 102. The controller 130 may store the data, provided by the host 102, into the memory device 150.

The controller 130 may include a host interface (I/F) 132, a processor 134, an error correction code (ECC) circuit 138, a power management unit (PMU) 140, a memory interface (If F) 142 and a memory 144, all operatively coupled via an internal bus.

The host interface 132 may process commands and data provided from the host 102, and may communicate with the host 102 through at least one of various interface protocols such as universal serial bus (USB), multimedia card (MMC), peripheral component interconnect-express (PCI-e or PCIe), small computer system interface (SCSI), serial-attached SCSI (SAS), serial advanced technology attachment (SATA), parallel advanced technology attachment (PATA), small computer system interface (SCSI), enhanced small disk interface (ESDI) and integrated drive electronics (IDE). In accordance with an embodiment, the host interface unit 132 is a component for exchanging data with the host 102, which may be implemented through a firmware called a host interface layer (HIL).

The ECC 138 can correct error bits of the data to be processed in (e.g., outputted from) the memory device 150, which may include an ECC encoder and an ECC decoder. Here, the ECC encoder can perform error correction encoding of data to be programmed in the memory device 150 to generate encoded data into which a parity bit is added and then stores the encoded data in memory device 150. The ECC decoder can detect and correct errors contained in data read from the memory device 150 when the controller 130 reads the data stored in the memory device 150. In other words, after performing error correction decoding on the data read from the memory device 150, the ECC circuit 138 can determine whether the error correction decoding has succeeded and output an instruction signal (e.g., a correction success signal or a correction fail signal). The ECC circuit 138 can use the parity bit which is generated during the ECC encoding process, for correcting the error bit of the read data. When the number of the error bits is greater than or equal to a threshold number of correctable error bits, the ECC circuit 138 may not correct error bits but may output an error correction fail signal indicating failure in correcting the error bits.

The ECC circuit 138 may perform an error correction operation based on a coded modulation such as a low density parity check (LDPC) code, a Bose-Chaudhuri-Hocquenghem (BCH) code, a turbo code, a Reed-Solomon (RS) code, a convolution code, a recursive systematic s code (RSC), a trellis-coded modulation (TCM), a Block coded modulation (BCM), and so on. The ECC circuit 138 may include all or some of circuits, modules, systems or devices for performing the error correction operation based on at least one of the above described codes.

The PMU 140 may manage an electrical power provided in the controller 130.

The memory interface 142 may serve as an interface for handling commands and data transferred between the controller 130 and the memory device 150, to allow the controller 130 to control the memory device 150 in response to a request delivered from the host 102. The memory interface 142 may generate a control signal for the memory device 150 and may process data entered into or outputted from the memory device 150 under the control of the processor 134 in a case when the memory device 150 is a flash memory and, in particular, when the memory device 150 is a NAND flash memory. The memory interface unit 142 can provide an interface for handling commands and data between the controller 130 and the memory device 150, for example, operations of NAND flash interface, in particular, operations between the controller 130 and the memory device 150. In accordance with an embodiment, the memory interface unit 142 can be implemented through a firmware called a Flash Interface Layer (FIL) as a component for exchanging data with the memory device 150.

The memory 144 may support operations performed by the memory system 110 and the controller 130. The memory 144 may store temporary or transactional data occurred or delivered for operations in the memory system 110 and the controller 130. The controller 130 may control the memory device 150 in response to a request from the host 102. The controller 130 may deliver data read from the memory device 150 into the host 102. The controller 130 may store data entered through the host 102 within the memory device 150. The memory 144 may be used to store data required for the controller 130 and the memory device 150 to perform operations such as read operations or program/write operations.

The memory 144 may be implemented with a volatile memory. The memory 144 may be implemented with a static random access memory (SRAM), a dynamic random access memory (DRAM) or both. Although FIG. 1 exemplifies the second memory 144 disposed within the controller 130, the embodiment is not limited thereto. That is, the memory 144 may be located inside or outside the controller 130. For instance, the memory 144 may be embodied by an external volatile memory having a memory interface transferring data and/or signals transferred between the memory 144 and the controller 130.

The memory 144 can store data necessary for performing operations such as data writing and data reading requested by the host 102 and/or data transfer between the memory device 150 and the controller 130 for background operations such as garbage collection and wear levelling as described above. In accordance with an embodiment, for supporting operations in the memory system 110, the memory 144 may include a program memory, a data memory, a write buffer/cache, a read buffer/cache, a data buffer/cache, a map buffer/cache, and the like.

The processor 134 may be implemented with a microprocessor or a central processing unit (CPU). The memory system 110 may include one or more processors 134. The processor 134 may control the overall operations of the memory system 110. By way of example but not limitation, the processor 134 can control a program operation or a read operation of the memory device 150, in response to a write request or a read request entered from the host 102. In accordance with an embodiment, the processor 134 may use or execute a firmware to control the overall operations of the memory system 110. Herein, the firmware may be referred to as a flash translation layer (FTL). The FTL may perform an operation as an interface between the host 102 and the memory device 150. The host 102 may transmit requests for write and read operations to the memory device 150 through the FTL.

The FTL may manage operations of address mapping, garbage collection, wear-leveling and so forth. Particularly, the FTL may load, generate, update, or store map data. Therefore, the controller 130 may map a logical address, which is entered from the host 102, with a physical address of the memory device 150 through the map data. The memory device 150 may look like a general storage device to perform a read or write operation because of the address mapping operation. Also, through the address mapping operation based on the map data, when the controller 130 tries to update data stored in a particular page, the controller 130 may program the updated data on another empty page and may invalidate old data of the particular page (e.g., update a physical address, corresponding to a logical address of the updated data, from the previous particular page to the another newly programmed page) due to a characteristic of a flash memory device. Further, the controller 130 may store map data for the new data into the FTL.

For example, when performing an operation requested from the host 102 in the memory device 150, the controller 130 uses the processor 134 implemented in a microprocessor or central processing unit (CPU) or the like. The processor 134 engaged with the memory device 150 can handle instructions or commands corresponding to an inputted command from the host 102. The controller 130 can perform a foreground operation as a command operation, corresponding to a command inputted from the host 102, such as a program operation corresponding to a write command, a read operation corresponding to a read command, an erase/discard operation corresponding to an erase/discard command and a parameter set operation corresponding to a set parameter command or a set feature command using a set command.

For another example, the controller 130 may perform a background operation on the memory device 150 through the processor 134. By way of example but not limitation, the background operation for the memory device 150 includes an operation (e.g., a garbage collection (GC) operation) for copying and storing data stored in an arbitrary memory block among the memory blocks 152, 154, 156 in the memory device 150 to another arbitrary memory block. The background operation can include an operation (e.g., a wear leveling (WL) operation) to move or swap between data stored in at least one of the memory blocks 152, 154, 156 in memory device 150 and in at least another of the memory blocks 152, 154, 156. As the background operation, the controller 130 uses the processor 134 for storing the map data stored in the controller 130 to at least one of the memory blocks 152, 154, 156 in the memory device 150, e.g., a map flush operation. A bad block management operation for checking bad blocks in the plurality of memory blocks 152, 154, 156 included in the memory device 150 is one of other background operation examples performed by the processor 134.

In accordance with an embodiment, the controller 130 and the second memory 144 shown in FIG. 1 may be implemented through at least one processor 134 and at least one memory 144 in the controller 130 described in FIG. 2.

In the memory system 110, the controller 130 performs a plurality of command operations corresponding to a plurality of commands entered from the host 102. For example, when performing a plurality of program operations corresponding to plural program commands, a plurality of read operations corresponding to plural read commands and a plurality of erase operations corresponding to plural erase commands sequentially, randomly or alternatively, the controller 130 can determine which channel(s) or way(s) in a plurality of channels (or ways) for connecting the controller 130 to a plurality of memory dies included in the memory 150 is/are proper or appropriate for performing each operation. The controller 130 can send or transmit data or instructions via determined channels or ways for performing each operation. The plurality of memory dies included in the memory 150 can transmit an operation result via the same channels or ways, respectively, after each operation is complete. Then, the controller 130 may transmit a response or an acknowledge signal to the host 102. In an embodiment, the controller 130 can check a status of each channel or each way. In response to a command entered from the host 102, the controller 130 may select at least one channel or way based on the status of each channel or each way so that instructions and/or operation results with data may be delivered via selected channel(s) or way(s).

By the way of example but not limitation, the controller 130 can recognize statuses regarding a plurality of channels (or ways) associated with a plurality of memory dies included in the memory device 150. The controller 130 may determine each channel or each way as one of a busy state, a ready state, an active state, an idle state, a normal state and/or an abnormal state. The controller's determination of which channel or way an instruction (and/or data) is delivered through can be associated with a physical block address, e.g., which die(s) the instruction (and/or the data) is delivered into. The controller 130 can refer to descriptors delivered from the memory device 150. The descriptors can include a block or page of parameters that describe something about the memory device 150, which is data with a predetermined format or structure. For instance, the descriptors may include device descriptors, configuration descriptors, unit descriptors, and the like. The controller 130 can refer to, or use, the descriptors to determine which channel(s) or way(s) an instruction or data is exchanged via.

A management unit (not shown) may be included in the processor 134. The management unit may perform bad block management of the memory device 150. The management unit may find bad memory blocks included in the memory device 150, which are in unsatisfactory condition for further use, as well as perform bad block management on the bad memory blocks. When the memory device 150 is a flash memory, for example, a NAND flash memory, a program failure may occur during the write operation, for example, during the program operation, due to characteristics of a NAND logic function. During the bad block management, the data of the program-failed memory block or the bad memory block may be programmed into a new memory block. The bad blocks may seriously aggravate the utilization efficiency of the memory device 150 having a 3D stack structure and the reliability of the memory system 110. Thus, reliable bad block management may enhance or improve performance of the s memory system 110.

Referring to FIG. 3, a controller in a memory system in accordance with another example of the disclosure is described in detail. The controller 130 cooperates with the host 102 and the memory device 150. The controller 130 can include a host interface unit 132, a flash translation layer (FTL) unit 40, a memory interface unit 142 and a memory 144.

Although not shown in FIG. 3, in accordance with an embodiment, the ECC circuit 138 described in FIG. 2 may be included in the flash translation layer (FTL) unit 40. In another embodiment, the ECC circuit 138 may be implemented as a separate module, a circuit, a firmware or the like, which is included in, or associated with, the controller 130.

The host interface unit 132 is for handling commands, data, and the like transmitted from the host 102. By way of example but not limitation, the host interface unit 132 can include a command queue 56, a buffer manager 52 and an event queue 54. The command queue 56 can sequentially store commands, data, and the like transmitted from the host 102 and output them to the buffer manager 52 in a stored order. The buffer manager 52 can classify, manage or adjust the commands, the data, and the like, which are delivered from the command queue 56. The event queue 54 can sequentially transmit events for processing the commands, the data, and the like transmitted from the buffer manager 52.

A plurality of commands or data of the same characteristic may be continuously transmitted from the host 102, or commands and data of different characteristics may be transmitted to the memory system 110 after being mixed or jumbled. For example, a plurality of commands for reading data (read commands) may be delivered, or commands for reading data (read command) and programming/writing data (write command) may be alternately transmitted to the memory system 110. The host interface unit 132 can store commands, data, and the like, which are transmitted from the host 102, to the command queue 56 sequentially. Thereafter, the host interface unit 132 can estimate or predict what kind of operation the controller 130 will perform according to the characteristics of the command, data, etc., which is transmitted from the host 102. The host interface unit 132 can determine a processing order and a priority of commands, data and the like, based at least on their characteristics. According to characteristics of commands, data, and the like transmitted from the host 102, the buffer manager 52 in the host interface unit 132 is configured to determine whether the buffer manager should store commands, data, and the like in the memory 144, or whether the buffer manager should deliver the commands, the data, and the like into the flash translation layer (FTL) unit 40. The event queue 54 receives events, entered from the buffer manager 52, which are to be internally executed and processed by the memory system 110 or the controller 130 in response to the commands, the data, etc., transmitted from the host 102, so as to deliver the events into the flash translation layer (FTL) unit 40 in the order received.

In accordance with an embodiment, the host interface unit 132 described in FIG. 3 may perform the functions of the controller 130 described in FIG. 1. The host interface unit 132 may set the first memory 104 included in the host 102 as a slave and add the first memory 104 as an additional storage space which is controllable or usable by the controller 130.

In accordance with an embodiment, the flash translation layer (FTL) unit 40 can include a host request manager (HRM) 46, a map manager (MM) 44, a state manager 42 and a block manager 48. The host request manager (HRM) 46 can manage the events entered from the event queue 54. The map manager (MM) 44 can handle or control a map data. The state manager 42 can perform garbage collection or wear leveling. The block manager 48 can execute commands or instructions onto a block in the memory device 150.

By way of example but not limitation, the host request manager (HRM) 46 can use the map manager (MM) 44 and the block manager 48 to handle or process requests according to the read and program commands, and events which are delivered from the host interface unit 132. The host request manager (HRM) 46 can send an inquiry request to the map data manager (MM) 44, to figure out a physical address corresponding to the logical address which is entered with the events. The host request manager (HRM) 46 can send a read request with the physical address to the memory interface unit 142, to process the read request (handle the events). On the other hand, the host request manager (HRM) 46 can sends a program request (write request) to the block manager 48, to program entered data to a specific page of the unrecorded (no data) in the memory device 150, and then, can transmit a map update request corresponding to the program request to the map manager (MM) 44, to update an item relevant to the programmed data in information of mapping the logical-physical addresses to each other.

Here, the block manager 48 can convert a program request delivered from the host request manager (HRM) 46, the map data manager (MM) 44, and/or the state manager 42 into a flash program request used for the memory device 150, to manage flash blocks in the memory device 150. In order to maximize or enhance program or write performance of the memory system 110 (see FIG. 2), the block manager 48 may collect program requests and send flash program requests for multiple-plane and one-shot program operations to the memory interface unit 142. It can be plausible that the block manager 48 sends several flash program requests to the memory interface unit 142 to enhance or maximize parallel processing of the multi-channel and multi-directional flash controller.

On the other hand, the block manager 48 can be configured to manage blocks in the memory device 150 according to the number of valid pages, select and erase blocks having no valid pages when a free block is needed, and select a block including the least valid page when it is determined that garbage collection is necessary. The state manager 42 can perform garbage collection to move the valid data to an empty block and erase the blocks containing the moved valid data so that the block manager 48 may have enough free blocks (empty blocks with no data). If the block manager 48 provides information regarding a block to be erased to the state manager 42, the state manager 42 could check all flash pages of the block to be erased to determine whether each page is valid. For example, to determine validity of each page, the state manager 42 can identify a logical address recorded in an out-of-band (00B) area of each page. To determine whether each page is valid, the state manager 42 can compare the physical address of the page with the physical address mapped to the logical address obtained from the inquiry request. The state manager 42 sends a program request to the block manager 48 for each valid page. A mapping table can be updated through the update of the map manager 44 when the program operation is complete.

The map manager 44 can manage a logical-physical mapping table. The map manager 44 can process requests such as queries, updates, and the like, which are generated by the host request manager (HRM) 46 or the state manager 42. The map manager 44 may store the entire mapping table in the memory device 150 (e.g., a flash/non-volatile memory) and cache mapping entries according to the storage capacity of the memory 144. When a map cache miss occurs while processing inquiry or update requests, the map manager 44 may send a read request to the memory interface unit 142 to load a relevant mapping table stored in the memory device 150. When the number of dirty cache blocks in the map manager 44 exceeds a certain threshold, a program request can be sent to the block manager 48 so that a clean cache block is made, and the dirty map table may be stored in the memory device 150.

On the other hand, when garbage collection is performed, the state manager 42 copies valid page(s) into a free block, and the host request manager (HRM) 46 can program the latest version of the data for the same logical address of the page, and currently issue an update request. When the status manager 42 requests the map update in a state in which copying of valid page(s) is not completed normally, the map manager 44 may not perform the mapping table update. It is because the map request is issued with old physical information if the status manger 42 requests a map update and a valid page copy is completed later. The map manager 44 may perform a map update operation to ensure accuracy only if the latest map table still points to the old physical address.

The memory device 150 can include a plurality of memory blocks. The plurality of memory blocks can be classified into different types of memory blocks such as a single level cell (SLC) memory block, a multi-level cell (MLC) Cell) memory block or the like, according to the number of bits that can be stored or represented in one memory cell. Here, the SLC memory block includes a plurality of pages implemented by memory cells, each storing one bit of data. The SLC memory block can have high data I/O operation performance and high durability. The MLC memory block includes a plurality of pages implemented by memory cells, each storing multi-bit data (e.g., two bits or more). The MLC memory block can have larger storage capacity in the same space than the SLC memory block. The MLC memory block can be highly integrated in view of storage capacity. In an embodiment, the memory device 150 may be implemented with MLC memory blocks such as an MLC memory block, a triple level cell (TLC) memory block, a quadruple level cell (QLC) memory block and a combination thereof. The MLC memory block may include a plurality of pages implemented by memory cells, each capable of storing 2-bit data. The triple level cell (TLC) memory block can include a plurality of pages implemented by memory cells, each capable of storing 3-bit data. The quadruple level cell (QLC) memory block can include a plurality of pages implemented by memory cells, each capable of storing 4-bit data. In another embodiment, the memory device 150 can be implemented with a block including a plurality of pages implemented by memory cells, each capable of storing 5-bit or more bit data.

In an embodiment of the disclosure, the memory device 150 is embodied as a nonvolatile memory such as a flash memory such as a NAND flash memory, a NOR flash memory and the like. But, the memory device 150 may also be implemented by at least one of a phase change random access memory (PCRAM), a ferroelectrics random access memory (FRAM), a spin injection magnetic memory (STT-RAM), and a spin transfer torque magnetic random access memory (S MRAM), or the like.

FIGS. 4 and 5 schematically describe an example of performing a plurality of command operations corresponding to a plurality of commands in the memory system in accordance with an embodiment of the disclosure. For example, in the embodiment of the disclosure, detailed descriptions will be made for a data processing operation in a case where a plurality of write commands are received from the host 102 and program operations corresponding to the write commands are performed, in another case where a plurality of read commands are received from the host 102 and read operations corresponding to the read commands are performed, in another case where a plurality of erase commands are received from the host 102 and erase operations corresponding to the erase commands are performed, or in another case where a plurality of write commands and a plurality of read commands are received together from the host 102, then program operations and read operations corresponding to the write commands and the read commands are performed.

Moreover, in the embodiment of the disclosure, descriptions will be made by taking as an example a case where: write data corresponding to a plurality of write commands entered from the host 102 are stored in the buffer/cache included in the memory 144 of the controller 130, the write data stored in the buffer/cache are programmed to and stored in the plurality of memory blocks included in the memory device 150, map data are updated which correspond to the stored write data in the plurality of memory blocks, and the updated map data are stored in the plurality of memory blocks included in the memory device 150. In the embodiment of the disclosure, descriptions will be made by taking as an example a case where program operations corresponding to a plurality of write commands entered from the host 102 are performed. Furthermore, in the embodiment of the disclosure, descriptions will be made by taking as an example a case where: a plurality of read commands are entered from the host 102 for the data stored in the memory device 150, data corresponding to the read commands are read from the memory device 150 by checking the map data of the data corresponding to the read commands, the read data are stored in the buffer/cache included in the memory 144 of the controller 130, and the data stored in the buffer/cache are provided to the host 102. In other words, in the embodiment of the disclosure, descriptions will be made by taking as an example a case where read operations corresponding to a plurality of read commands entered from the host 102 are performed. In addition, in the embodiment of the disclosure, descriptions will be made by taking as an example a case where: a plurality of erase commands are received from the host 102 for the memory blocks included in the memory device 150, memory blocks are checked corresponding to the erase commands, the data stored in the checked memory blocks are erased, map data are updated which correspond to the erased data, and the updated map data are stored in the plurality of memory blocks included in the memory device 150. Namely, in the embodiment of the disclosure, descriptions will be made by taking as an example a case where erase operations corresponding to a plurality of erase commands received from the host 102 are performed.

Further, while, in the embodiment of the disclosure, it will be described below as an example that the controller 130 performs command operations in the memory system 110, it is to be noted that, as described above, the processor 134 included in the controller 130 may perform command operations in the memory system 110, through, for example, an FTL (flash translation layer). Also, in the embodiment of the disclosure, the controller 130 programs and stores user data and metadata corresponding to write commands entered from the host 102, in arbitrary memory blocks among the plurality of memory blocks included in the memory device 150, reads user data and metadata corresponding to read commands received from the host 102, from arbitrary memory blocks among the plurality of memory blocks included in the memory device 150, and provides the read data to the host 102, or erases user data and metadata, corresponding to erase commands entered from the host 102, from arbitrary memory blocks among the plurality of memory blocks included in the memory device 150.

Metadata may include first map data including a logical/physical (L2P: logical to physical) information (hereinafter, referred to as a ‘logical information’) and second map data including a physical/logical (P2L: physical to logical) information (hereinafter, referred to as a ‘physical information’), for data stored in memory blocks corresponding to a program operation. Also, the metadata may include an information on command data corresponding to a command received from the host 102, an information on a command operation corresponding to the command, an information on the memory blocks of the memory device 150 for which the command operation is to be performed, and an information on map data corresponding to the command operation. In other words, metadata may include all remaining information and data excluding user data corresponding to a command received from the host 102.

That is, in the embodiment of the disclosure, in the case where: the controller 130 receives a plurality of write commands from the host 102, program operations corresponding to the write commands are performed, and user data corresponding to the write commands are written and stored in empty memory blocks, open memory blocks or free memory blocks for which an erase operation has been performed, among the memory blocks of the memory device 150. Also, first map data, including an L2P map table or an L2P map list in which logical information as the mapping information between logical addresses and physical addresses for the user data stored in the memory blocks are recorded, and second map data, including a P2L map table or a P2L map list in which physical information as the mapping information between physical addresses and logical addresses for the memory blocks stored with the user data are recorded, are written and stored in empty memory blocks, open memory blocks or free memory blocks among the memory blocks of the memory device 150.

Here, in the case where write commands are entered from the host 102, the controller 130 writes and stores user data corresponding to the write commands in memory blocks. The controller 130 stores, in other memory blocks, metadata including first map data and second map data for the user data stored in the memory blocks. Particularly, corresponding to the data segments of the user data which are stored in the memory blocks of the memory device 150, the controller 130 generates and updates the L2P segments of first map data and the P2L segments of second map data as the map segments of map data among the meta segments of metadata. The controller 130 stores the meta segments in the memory blocks of the memory device 150. The map segments stored in the memory blocks of the memory device 150 are loaded in the memory 144 included in the controller 130 and are then updated.

Further, in the case where a plurality of read commands are received from the host 102, the controller 130 reads read data corresponding to the read commands, from the memory device 150, stores the read data in the buffers/caches included in the memory 144 of the controller 130. The controller 130 provides the data stored in the buffers/caches, to the host 102, by which read operations corresponding to the plurality of read commands are performed.

In addition, in the case where a plurality of erase commands are received from the host 102, the controller 130 checks memory blocks of the memory device 150 corresponding to the erase commands, and then, performs erase operations for the memory blocks.

When command operations corresponding to the plurality of commands received from the host 102 are performed while a background operation is performed, the controller 130 loads and stores data corresponding to the background operation, that is, metadata and user data, in the buffer/cache included in the memory 144 of the controller 130, and then stores the data, that is, the metadata and the user data, in the memory device 150. Herein, by way of example but not limitation, the background operation may include a garbage collection operation or a read reclaim operation as a copy operation, a wear leveling operation as a swap operation or a map flush operation. For instance, for the background operation, the controller 130 may check metadata and user data corresponding to the background operation, in the memory blocks of the memory device 150, load and store the metadata and user data stored in certain memory blocks of the memory device 150, in the buffer/cache included in the memory 144 of the controller 130, and then store the metadata and user data, in certain other memory blocks of the memory device 150.

In the memory system in accordance with the embodiment of the disclosure, in the case of performing command operations as foreground operations and a copy operation, a swap operation and a map flush operation as background operations, the controller 130 schedules queues corresponding to the foreground operations and the background operations and allocates the scheduled queues to the memory 144 included in the controller 130 and the memory included in the host 102. In this regard, the controller 130 assigns identifiers (IDs) by respective operations for the foreground operations and the background operations to be performed in the memory device 150, and schedules queues corresponding to the operations assigned with the identifiers, respectively. In the memory system in accordance with the embodiment of the disclosure, identifiers are assigned not only by respective operations for the memory device 150 but also by functions for the memory device 150, and queues corresponding to the functions assigned with respective identifiers are scheduled.

In the memory system in accordance with the embodiment of the disclosure, the controller 130 manages the queues scheduled by the identifiers of respective functions and operations to be performed in the memory device 150. The controller 130 manages the queues scheduled by the identifiers of a foreground operation and a background operation to be performed in the memory device 150. In the memory system in accordance with the embodiment of the disclosure, after memory regions corresponding to the queues scheduled by identifiers are allocated to the memory 144 included in the controller 130 and the memory included in the host 102, the controller 130 manages addresses for the allocated memory regions. The controller 130 performs not only the foreground operation and the background operation but also respective functions and operations in the memory device 150, by using the scheduled queues.

Referring to FIG. 4, the controller 130 performs command operations corresponding to a plurality of commands entered from the host 102, for example, program operations corresponding to a plurality of write commands entered from the host 102. At this time, the controller 130 programs and stores user data corresponding to the write commands, in memory blocks of the memory device 150. Also, corresponding to the program operations with respect to the memory blocks, the controller 130 generates and updates metadata for the user data and stores the metadata in the memory blocks of the memory device 150.

The controller 130 generates and updates first map data and second map data which include information indicating that the user data are stored in pages included in the memory blocks of the memory device 150. That is, the controller 130 generates and updates L2P segments as the logical segments of the first map data and P2L segments as the physical segments of the second map data, and then stores the logical and physical segments in pages included in the memory blocks of the memory device 150.

For example, the controller 130 caches and buffers the user data corresponding to the write commands entered from the host 102, in a first buffer 510 included in the memory 144 of the controller 130. Particularly, after storing data segments 512 of the user data in the first buffer 510 worked as a data buffer/cache, the controller 130 stores the data segments 512 stored in the first buffer 510 in pages included in the memory blocks of the memory device 150. As the data segments 512 of the user data corresponding to the write commands received from the host 102 are programmed to and stored in the pages included in the memory blocks of the memory device 150, the controller 130 generates and updates the first map data and the second map data. The controller 130 stores the first and second map data in a second buffer 520 included in the memory 144 of the controller 130. Particularly, the controller 130 stores L2P segments 522 of the first map data and P2L segments 524 of the second map data for the user data, in the second buffer 520 as a map buffer/cache. As described above, the L2P segments 522 of the first map data and the P2L segments 524 of the second map data may be stored in the second buffer 520 of the memory 144 in the controller 130. A map list for the L2P segments 522 of the first map data and another map list for the P2L segments 524 of the second map data may be stored in the second buffer 520. The controller 130 stores the L2P segments 522 of the first map data and the P2L segments 524 of the second map data, which are stored in the second buffer 520, in pages included in the memory blocks of the memory device 150.

Also, the controller 130 performs command operations corresponding to a plurality of commands received from the host 102, for example, read operations corresponding to a plurality of read commands received from the host 102. Particularly, the controller 130 loads L2P segments 522 of first map data and P2L segments 524 of second map data as the map segments of user data corresponding to the read commands, in the second buffer 520, and checks the L2P segments 522 and the P2L segments 524. Then, the controller 130 reads the user data stored in pages of corresponding memory blocks among the memory blocks of the memory device 150, stores data segments 512 of the read user data in the first buffer 510, and then provides the data segments 512 to the host 102.

Furthermore, the controller 130 performs command operations corresponding to a plurality of commands entered from the host 102, for example, erase operations corresponding to a plurality of erase commands entered from the host 102. In particular, the controller 130 checks memory blocks corresponding to the erase commands among the memory blocks of the memory device 150 to carry out the erase operations for the checked memory blocks.

In the case of performing an operation of copying data or swapping data among the memory blocks included in the memory device 150, for example, a garbage collection operation, a read reclaim operation or a wear leveling operation, as a background operation, the controller 130 stores data segments 512 of corresponding user data, in the first buffer 510, loads map segments 522, 524 of map data corresponding to the user data, in the second buffer 520, and then performs the garbage collection operation, the read reclaim operation or the wear leveling operation. In the case of performing a map update operation and a map flush operation for metadata, e.g., map data, for the memory blocks of the memory device 150 as a background operation, the controller 130 loads the corresponding map segments 522, 524 in the second buffer 520, and then performs the map update operation and the map flush operation.

As aforementioned, in the case of performing functions and operations including a foreground operation and a background operation for the memory device 150, the controller 130 assigns identifiers by the functions and operations to be performed for the memory device 150. The controller 130 schedules queues respectively corresponding to the functions and operations assigned with the identifiers, respectively. The controller 130 allocates memory regions corresponding to the respective queues, to the memory 144 included in the controller 130 and the memory included in the host 102. The controller 130 manages the identifiers assigned to the respective functions and operations, the queues scheduled for the respective identifiers and the memory regions allocated to the memory 144 of the controller 130 and the memory of the host 102 which correspond to the queues, respectively. The controller 130 performs the functions and operations for the memory device 150, through the memory regions allocated to the memory 144 of the controller 130 and the memory of the host 102.

Referring to FIG. 5, the memory device 150 includes a plurality of memory dies, for example, a memory die 0, a memory die 1, a memory die 2 and a memory die 3, and each of the memory dies includes a plurality of planes, for example, a plane 0, a plane 1, a plane 2 and a plane 3. The respective planes in the memory dies included in the memory device 150 include a plurality of memory blocks, for example, N number of blocks Block0, Block1, . . . , BlockN−1 each including a plurality of pages, for example, 2^(M) number of pages, as described above with reference to FIG. 3. Moreover, the memory device 150 includes a plurality of buffers corresponding to the respective memory dies, for example, a buffer 0 corresponding to the memory die 0, a buffer 1 corresponding to the memory die 1, a buffer 2 corresponding to the memory die 2 and a buffer 3 corresponding to the memory die 3.

In the case of performing command operations corresponding to a plurality of commands received from the host 102, data corresponding to the command operations are stored in the buffers included in the memory device 150. For example, in the case of performing program operations, data corresponding to the program operations are stored in the buffers, and are then stored in the pages included in the memory blocks of the memory dies. In the case of performing read operations, data corresponding to the read operations are read from the pages included in the memory blocks of the memory dies, are stored in the buffers, and are then provided to the host 102 through the controller 130.

In the embodiment of the disclosure, the buffers included in the memory device 150 exist outside the respective corresponding memory dies, however, it is to be noted that the buffers may exist inside the respective corresponding memory dies, and it is to be noted that the buffers may correspond to the respective planes or the respective memory blocks in the respective memory dies. Further, in the embodiment of the disclosure, the buffers included in the memory device 150 are the plurality of page buffers 322, 324, and 326 included in the memory device 150 as described above with reference to FIG. 3, however, it is to be noted that the buffers may be a plurality of caches or a plurality of registers included in the memory device 150.

Also, the plurality of memory blocks included in the memory device 150 may be grouped into a plurality of super memory blocks, and command operations may be performed in the plurality of super memory blocks. Each of the super memory blocks may include a plurality of memory blocks, for example, memory blocks included in a first memory block group and a second memory block group. In this regard, in the case where the first memory block group is included in the first plane of a certain first memory die, the second memory block group may be included in the first plane of the first memory die, be included in the second plane of the first memory die or be included in the planes of a second memory die.

In an embodiment of the disclosure, a data processing system may include plural memory systems. Each of the plural memory systems 110 can include the controller 130 and the memory device 150. In the data processing system, one of the plural memory systems 110 can be a master and the others can be a slave. The master may be determined based on contention between the plural memory systems 110. When a plurality of commands is delivered from the host 102 in the data processing system, the master can determine a destination of each command based at least on statuses of channels or buses. For example, a first memory system can be determined as a master memory system among a plurality of memory systems, corresponding to information delivered from the plurality of memory systems. If the first memory system is determined as the master memory system, the remaining memory systems are considered slave memory systems. A controller of the master memory system can check statuses of a plurality of channels (or ways, buses) coupled to a plurality of memory systems, to select which memory system handles commands or data delivered from the host 102. In an embodiment, a master can be dynamically determined among the plural memory systems. In another embodiment, a master memory system may be changed with one of other slave memory systems periodically or according to an event.

Hereinafter, a method and apparatus for transferring data in the memory system 110 including the memory system 150 and the controller 130 described above will be described in more detail. As the amount of data stored in the memory system 110 becomes larger, and the memory system 110 may be required to read or store large amounts of data at a time. However, a read time for reading data stored in the memory device 150 or a program/write time for writing data in the memory device 150 may be generally longer than a handling time for the controller 130 to process data or a data transmission time between the controller 130 and the memory system 150. For example, the read time might be twice that of the handling time. Since the read time or the program time is relatively far longer than the handling time or the data transmission time, a procedure or a process for delivering data in the memory system 110 may affect performance of the memory system 110, e.g., an operation speed, and/or structure of the memory system 110 such as a buffer size.

In FIG. 6, a host 10 and a memory system 20 in accordance with an embodiment of the disclosure are described. The host 10, the memory system 20 and other components can be constituted with a data processing system in accordance with an embodiment of the disclosure. In a computing device or a mobile device embedded with the memory system 20, the memory system 20 is engaged with the host 10 to exchange data.

Referring to FIG. 6, the memory system 20 can include a controller 30 and a memory device 40. The controller 30 receives and outputs data, requested from the host 10, from the memory device 40 or stores the data transferred from the host 10 into the memory device 40 in order to perform command operations requested from the host 10. The memory device 40 includes a plurality of memory cells capable of storing data. Here, the internal configuration of the memory device 40 can be changed in accordance with the characteristics of the memory device 40, the purposes for which the memory system 20 is used, the specifications of the memory system 20 required by the host 10, or the like.

For example, the memory device 150 illustrated in FIGS. 1-5 and the memory device 40 of FIG. 6 may include the same components. In addition, the controller 130 described in FIGS. 1 through 5 and the controller 30 shown in FIG. 6 may include the same components.

The controller 30 may include at least one processor 34, a host interface 36, a buffer 28, and a controller interface 32. The processor 34, for command operations within the controller 30, can play a role similar to that of a CPU used in a computing device. The host interface 36 is for data communication between the memory system 20 and the host 10, while the controller interface 32 is for data communication between the memory device 40 and the controller 30. The memory 38 temporarily stores the data and operation status required during operations performed by the processor 34, the host interface 36 and the controller interface 32. Or, the memory 38 can temporarily store I/O data between the memory device 40 and the host 10. The internal configuration of the above-described controller 30 may be a function classification according to an operation, a task, or the like which is handled or processed by the controller.

In accordance with an embodiment, the physical configuration of the controller 30 may be composed of at least one processor, at least one memory, at least one input/output port, and a wiring for electrical connection between the above-mentioned components.

The controller 30 and the memory device 40 can exchange a metadata and a user data with each other. Here, the user data includes data to be stored by a user through the host 10, and the metadata includes system information (e.g., map data and the like) necessary for storing and managing the user data in the memory device 40. The user data and the meta data can be processed or managed in different ways in the controller 30 because the properties of the user data and the meta data are different from each other.

As a storage capacity of the memory device 40 increases, the status information and the like have bigger sizes, which can include system information, map information, and/or operation information necessary for operations such as reading, programming, and erasing data within a plurality of dies, a plurality of blocks, or a plurality of pages included in the memory device 40. It is difficult for the controller 30 to store all the status information and the like in the memory 38. Thus, the system information, the map information, the operation information, and the like for operation such as reading, programming, erasing, etc., as well as user data, may be stored in the memory device s 40. The controller 30 may load, from the plurality of dies, blocks in the memory device 40, some information necessary for operations such as reading, programming, or deleting data in a plurality of pages from the memory device 40, and then re-stores the updated information in the memory device 40 after the corresponding operation is completed.

Although not shown, as the number of memory cells capable of storing data in the memory device 40 increases, the internal structure of the memory device 40 can be complicated as described in FIG. 6. The controller 30 may transmit or receive connection information according to the internal configuration of the memory device 40 together with the data. For example, in a case when a plurality of dies is included in the memory device 40 as shown in FIG. 6, there are n channels and m ways (n, m are integers greater than 1) between the controller 30 and the memory device 40. The data and the connection information may be transferred via the n channels and the m ways. However, in order for the controller 30 to read or write data to the memory device 40, additional control variables or control signals may be needed depending on the internal structure of the memory device 40. As more dies are included in the memory device 40, additional information required for performing operations becomes larger.

As described above, the memory system 20 in accordance with an embodiment includes the memory device 40 including a plurality of memory blocks including a plurality of pages in which data is stored, and the controller 30 for executing command operations corresponding to the plurality of commands. Herein, the controller 30 may load data from a plurality of first memory blocks in the memory device 40 and exclude the plurality of first memory blocks in the block in a plurality of second memory block to be programmed by loaded, updated or new data generated through internal or external command operations. The command operations can include a foreground operation and a background operation performed within the memory device 40. The foreground operation and the background operation may include a data program operation, a data delete operation, a data read operation and the like. Even though some of the data outputted from first memory blocks are erased or discarded and some of the first memory blocks become a free block, the controller 30 does not allocate some of the first memory blocks as a second memory block to be programmed by data which were originally stored in the first memory blocks and are now transferred, moved or updated. When the updated data is stored in the second memory block previously secured and the command operation is completed, the first memory block which is erased or discarded can be used as the second memory block to be programmed with another data corresponding to a next operation. Further, the controller 30 can sequentially store information regarding command operations in the second memory block before the power supply is interrupted, e.g., a sudden power off (SPO). After power-on, the controller 30 sequentially loads the information stored in the second memory block to resume the command operations.

FIGS. 7 to 9 illustrate different examples of how to generate the free block list 37. In FIGS. 7 to 9, a plurality of data blocks 40_1 and a plurality of free blocks 40_2 are included in the memory device 150. Furthermore, six blocks BLK15, BLK17, BLK25, BLK29, BLK31 and BLK36 of the plurality of data blocks 40_1 are the data blocks for a single operation of programming or moving a large amount of data. Here, the six blocks BLK15, BLK17, BLK25, BLK29, BLK31, and BLK36 may be referred to as blocks-in-use. A plurality of blocks BLK11, BLK23 and BKL30 other than the blocks-in-use among the plurality of data blocks 40_1 may be referred to as blocks-not-in-use. Meanwhile, the controller 130 (see FIGS. 1 to 3) can recognize or determine a block as one of a block-in-use, a block-not-in-use and a free block, before performing an operation of programming a large amount of data.

Referring to FIG. 7, the controller 130 may generate the free block list 37 before performing at least one operation to program or transfer a large amount of data. The free block list 37 may include information on a plurality of free blocks 40_2 in the memory device 150. In accordance with an embodiment, the free block list 37 may include information on all free blocks 40_2 in the memory device 150. The free blocks BLK33, BLK12, BLK9, BLK39, BLK26, BLK21 included in the free block list 37 can be prioritized and sorted according to driving information, status information, or the like. For example, the free blocks BLK33, BLK12, BLK9, BLK39, BLK26, BLK21, information on which is included in the free block list 37, may have a higher priority in the free block list 37 as an erase count of each block is smaller. The high priority block BLK33 can be used first for at least one operation of programming or moving a larger capacity data than the non-priority blocks BLK12, BLK9, BLK39, BLK26, BLK21.

The free block list 37 generated before performing at least one operation of programming or moving a large amount of data may not be updated until the corresponding operation is completed. For this purpose, the controller 130 may allow the free block list 37 to include a predetermined number of free blocks. Depending on an embodiment, the predetermined number may be greater than the number of blocks required to store the amount of data that the controller 130 can program in a single operation. A predetermined number may be determined according to storage capacity of each block.

After being generated before the operation is begun, the free block list 37 may not be updated until the corresponding operation is completed. Accordingly, even if the current operation is not normally completed due to an unexpected event such as a power supply interruption, the risk of data being distorted when starting up again and creating the free block list 37 can be avoided. Also, in accordance with an embodiment, even if the free block list 37 is backed up to the memory device 150 before an event such as abrupt power supply interruption occurs, the memory system restarts and loads the free block list 37 so that the risk of data being distorted when resuming can be reduced.

FIG. 8 illustrates another embodiment for generating the free block list 37.

Referring to FIG. 8, the free block list 37 may be updated during the at least one operation for programming or moving a large amount of data stored in a plurality of blocks-in-use BLK15, BLK17, BLK25, BLK29, BLK31, BLK36.

One or more blocks BLK23, BLK36 can be changed to free blocks among a plurality of data blocks 40_1 during at least one operation for programming or moving a large amount of data stored in the plurality of blocks-in-use BLK15, BLK17, BLK25, BLK29, BLK31. If the free block list 37 can be updated during the process of performing at least one operation, the blocks BLK23, BLK36 changed from the data block to the free block can be added to the free block list 37. However, the block-in-use BLK36 cannot be added to the free block list 37 even if changed to the free block during the process of performing at least one operation. Instead, the block-not-in-use BLK23 may be added to the free block list 37 when changed to the free block during the process of performing at least one operation regardless of the process.

After the process of performing the operations associated with the plurality of used blocks BLK15, BLK17, BLK25, BLK29, BLK31, BLK36 is completed, a block BLK 36 changed from the used block to the free block may be added to the free block list 37.

In an embodiment of dynamically updating the free block list 37, it is possible to avoid, by excluding from the free block list 37 a block-in-use, which is changed to a free block during the currently performed operation, the risk of losing data even though the currently performed operation is not normally completed due to an unexpected event.

FIG. 9 illustrates another example of generating the free block list 37.

Referring to FIG. 9, the free block list 37 can be updated at any time via the controller 130 (See, FIGS. 1 to 3 and 6). When a free block in the memory device 150 is generated, information of the newly generated free block can be added to the free block list 37. However, the free block list 37 may include an additional flag or section.

In accordance with an embodiment, the free block list 37 may simply list the free blocks or sort the free blocks according to priority. The free block list 37 may include information of newly generated free blocks. In accordance with an embodiment of the present invention, the information of the free blocks in the free block list 37 may be rearranged based at least on the priority order whenever information of a free block is newly added.

The free block list 37 may include free block information (e.g., addresses of the free blocks BLK9, BLK12, BLK26, BLK21, BLK33, BLK39, BLK36 and BLK23 and bit information (“1” or “0”) corresponding to each free block. For example, before the controller 130 performs at least one operation to program or move a large amount of data, a plurality of free blocks BLK9, BLK12, BLK26, BLK21, BLK33 and BLK39 has bit information of “1,” which indicate that that the corresponding free block is available for the at least one operation that controller 130 is currently performing. However, the bit information of “0” may indicate the corresponding free block that is not available for the operation that controller 130 is currently performing.

Meanwhile, the data blocks BLK23 and BLK36 changed to free blocks during the operation of the controller 130 may be included in the free block list 37. However, the block-in-use BLK36 changed to the free block has bit information of “0”. Instead, the block-not-in-use BLK23 changed to the free block may have bit information of “1”. The controller 130 cannot use the free block BLK36 having the bit information of “0” for the current operation, while the free block BLK23 having the bit information of “1” can be used for the current operation to program a voluminous data.

In an embodiment in which the free block list 37 is updated dynamically, the free block list 37 can include bit information indicating whether each free block is available for the currently performed operation. It is possible to avoid using at least one block for the currently performed operation even if the at least one block changed into the block are included in the free block list 37. This can avoid the risk of losing data in an event that the current operation is not completed normally due to an event such as sudden power supply interruption.

Referring to FIGS. 7 to 9, the controller 130 generates the free block list 37 to determine whether the free block is available for the currently performed operation, so that it is possible to prevent the risk of losing data when the current operation is abnormally terminated. The operation stability of the memory system 20 can be improved or enhanced.

FIG. 10 illustrates a method of operating the memory system 20 in accordance with another embodiment of the disclosure.

Referring to FIG. 10, a method of operating the memory system 20 includes step 82 of receiving a plurality of commands, entered from the host 10, in association with the memory device 20 including a plurality of memory blocks each including a plurality of pages in which data is stored, step 84 of loading data from first memory blocks 40_1 among the plurality of memory blocks to perform command operations corresponding to the plurality of commands, and step 86 of allocating second memory blocks 40_2 storing updated data after the command operations are executed. Here, the first memory blocks 40_1 may be considered as storing data associated with the current command operation in the memory device 150. Also, the second memory blocks 40_2 can be considered free blocks available for large amounts of data generated, updated or transferred through the current command operation.

On the other hand, even if some of the first memory blocks 40_1 become free blocks during the current operation, the some of the first memory blocks may not be used as the free blocks until the current operation is normally terminated and the updated data is stored.

In addition, step 86 of allocating the second memory blocks 40_2 may include step 88 of generating a sorted list of the second memory blocks 40_2. The list may include information regarding availability of the second memory block 40_2, i.e., bit information corresponding to each memory block. Depending on an embodiment, the list may include only block information (e.g., block addresses). Also, the list may sort or arrange the information of the second memory blocks based on a priority order.

For example, the list can be updated due to a newly generated free block. In another example, the list may be generated before the command operations are begun and not updated while the command operations are being performed. Also, when at least one block other than the plurality of first memory blocks is changed to the second memory block during the command operations, the list may be updated to include the at least one of the plurality of blocks.

Although not shown, information on command operations is sequentially stored in the second memory block before a sudden power-off occurs. When a power is supplied, the information regarding the command operations stored in the second memory block may be loaded sequentially. In an embodiment, the information on the availability of the first memory block and/or the second memory block can be managed by a bitmap-type free block list 37 including bit information, each corresponding to each memory block. To manage the free block list 37, the operation method can include the steps of controlling the free block list 37 to include a first value indicating that a memory block is used as free blocks during the command operation, and a second value showing that a memory block becomes a free block at or after the start of the command operation.

Here, the first memory block may include a plurality of memory blocks each storing data, and the second memory block may include a plurality of free memory blocks that do not store any data.

In accordance with an embodiment, the data loaded from the first memory blocks and the updated data stored in the second memory block may be associated with corresponding map data. Depending on an embodiment, the map data may include a first map data for mapping a logical block address to a physical block address and a second map data for mapping the physical block address to the logical block address.

In accordance with an embodiment, the command operations may include a foreground operation and a background operation performed within the memory device. For example, the foreground operation and the background operation may include a data program operation, a data erase operation, or a data read operation, respectively.

As described above, a large amount of data in the memory system 20 can be moved or transferred for various purposes such as wear leveling and garbage collection. To transfer a large amount of data, a large amount of data must be programmed, which may take some time. In this process, the program operation of the large amount of data may be interrupted due to the interruption of the power supply. Accordingly, the controller 30 can generate and store bitmap-type information for determining whether a free block is available according to a current data storage state of a plurality of memory blocks (i.e., indicating availability for current command operations). Herein, the bitmap-type information may not take up too much resource. Even if some of the first memory blocks become free blocks, it is possible to control not to use the free blocks for the current command operations. Further, by referring to the bitmap-type information, data can be programmed into a memory block following the free block without scanning all the memory blocks even if the power is turned on again after power-off, thereby improving the stability and reliability of the memory system.

In FIG. 11, another example of the data processing system including the memory system in accordance with the embodiment is described. FIG. 11 schematically illustrates a memory card system to which the memory system in accordance with the embodiment is applied.

Referring to FIG. 11, the memory card system 6100 may include a memory controller 6120, a memory device 6130 and a connector 6110.

The memory controller 6120 may be connected to the memory device 6130 embodied by a nonvolatile memory. The memory controller 6120 may be configured to access the memory device 6130. By way of example but not limitation, the memory controller 6120 may be configured to control read, write, erase and background operations of the memory device 6130. The memory controller 6120 may be configured to provide an interface between the memory device 6130 and a host, and use a firmware for controlling the memory device 6130, That is, the memory controller 6120 may correspond to the controller 130 of the memory system 110 described with reference to FIGS. 1 and 3, and the memory device 6130 may correspond to the memory device 150 of the memory system 110 described with reference to FIGS. 1 and 5.

Thus, the memory controller 6120 may include a RAM, a processing unit, a host interface, a memory interface and an error correction unit. The memory controller 130 may further include the elements shown in FIGS. 1 and 3.

The memory controller 6120 may communicate with an external device, for example, the host 102 of FIG. 1 through the connector 6110. For example, as described with reference to FIGS. 1 to 3, the memory controller 6120 may be configured to communicate with an external device under one or more of various communication protocols such as universal serial bus (USB), multimedia card (MMC), embedded MMC (eMMC), peripheral component interconnection (PCI), PCI express (PCIe), Advanced Technology Attachment (ATA), Serial-ATA, Parallel-ATA, small computer system interface (SCSI), enhanced small disk interface (EDSI), Integrated Drive Electronics (IDE), Firewire, universal flash storage (UFS), WIFI and Bluetooth. Thus, the memory system and the data processing system in accordance with the present embodiment may be applied to wired/wireless electronic devices, particularly mobile electronic devices.

The memory device 6130 may be implemented by a nonvolatile memory. For example, the memory device 6130 may be implemented by various nonvolatile memory devices such as an erasable and programmable ROM (EPROM), an electrically erasable and programmable ROM (EEPROM), a NAND flash memory, a NOR flash memory, a phase-change RAM (PRAM), a resistive RAM (ReRAM), a ferroelectric RAM (FRAM) and a spin torque transfer magnetic RAM (STT-RAM). The memory device 6130 may include a plurality of dies as in the memory device 150 of FIG. 5.

The memory controller 6120 and the memory device 6130 may be integrated into a single semiconductor device. For example, the memory controller 6120 and the memory device 6130 may construct a solid state driver (SSD) by being integrated into a single semiconductor device. Also, the memory controller 6120 and the memory device 6130 may construct a memory card such as a PC card (PCMCIA: Personal Computer Memory Card International Association), a compact flash (CF) card, a smart media card (e.g., a SM and a SMC), a memory stick, a multimedia card (e.g., a MMC, a RS-MMC, a MMCmicro and an eMMC), an SD card (e.g., a SD, a miniSD, a microSD and a SDHC) and a universal flash storage (UFS).

FIG. 12 is a diagram schematically illustrating another example of the data processing system including the memory system in accordance with the embodiment.

Referring to FIG. 12, the data processing system 6200 may include a memory device 6230 having one or more nonvolatile memories and a memory controller 6220 for controlling the memory device 6230. The data processing system 6200 illustrated in FIG. 12 may serve as a storage medium such as a memory card (CF, SD, micro-SD or the like) or USB device, as described with reference to FIGS. 1 and 2. The memory device 6230 may correspond to the memory device 150 in the memory system 110 illustrated in FIGS. 1 and 5. The memory controller 6220 may correspond to the controller 130 in the memory system 110 illustrated in FIGS. 1 and 5.

The memory controller 6220 may control a read, write or erase operation on the memory device 6230 in response to a request of the host 6210. The memory controller 6220 may include one or more CPUs 6221, a buffer memory such as RAM 6222, an ECC circuit 6223, a host interface 6224 and a memory interface such as an NVM interface 6225.

The CPU 6221 may control overall operations on the memory device 6230, for example, read, write, file system management and bad page management operations. The RAM 6222 may be operated according to control of the CPU 6221. The RAM 6222 may be used as a work memory, buffer memory or cache memory. When the RAM 6222 is used as a work memory, data processed by the CPU 6221 may be temporarily stored in the RAM 6222. When the RAM 6222 is used as a buffer memory, the RAM 6222 may be used for buffering data transmitted to the memory device 6230 from the host 6210 or transmitted to the host 6210 from the memory device 6230. When the RAM 6222 is used as a cache memory, the RAM 6222 may assist the low-speed memory device 6230 to operate at high speed.

The ECC circuit 6223 may correspond to the ECC circuit 138 of the controller 130 illustrated in FIG. 1. As described with reference to FIG. 1, the ECC circuit 6223 may generate an ECC (Error Correction Code) for correcting a fail bit or error bit of data provided from the memory device 6230. The ECC circuit 6223 may perform error correction encoding on data provided to the memory device 6230, thereby forming data with a parity bit. The parity bit may be stored in the memory device 6230. The ECC circuit 6223 may perform error correction decoding on data outputted from the memory device 6230. At this time, the ECC circuit 6223 may correct an error using the parity bit. For example, as described with reference to FIG. 1, the ECC circuit 6223 may correct an error using the LDPC code, BCH code, turbo code, Reed-Solomon code, convolution code, RSC or coded modulation such as TCM or BCM.

The memory controller 6220 may transmit/receive data to/from the host 6210 through the host interface 6224. The memory controller 6220 may transmit/receive data to/from the memory device 6230 through the NVM interface 6225. The host interface 6224 may be connected to the host 6210 through a PATA bus, SATA bus, SCSI, USB, PCIe or NAND interface. The memory controller 6220 may have a wireless communication function with a mobile communication protocol such as WiFi or Long Term Evolution (LTE). The memory controller 6220 may be connected to an external device, for example, the host 6210 or another external device, and then transmit/receive data to/from the external device. Particularly, as the memory controller 6220 is configured to communicate with the external device through one or more of various communication protocols, the memory system and the data processing system in accordance with the present embodiment may be applied to wired/wireless electronic devices, particularly a mobile electronic device.

FIG. 13 is a diagram schematically illustrating another example of the data processing system including the memory system in accordance with the embodiment. FIG. 13 schematically illustrates an SSD to which the memory system in accordance with the embodiment is applied.

Referring to FIG. 13, the SSD 6300 may include a controller 6320 and a memory device 6340 including a plurality of nonvolatile memories. The controller 6320 may correspond to the controller 130 in the memory system 110 of FIGS. 1 and 2. The memory device 6340 may correspond to the memory device 150 in the memory system of FIGS. 1 and 5.

More specifically, the controller 6320 may be connected to the memory device 6340 through a plurality of channels CH1 to CHi. The controller 6320 may include one or more processors 6321, a buffer memory 6325, an ECC circuit 6322, a host interface 6324 and a memory interface, for example, a nonvolatile memory interface 6326.

The buffer memory 6325 may temporarily store data provided from the host 6310 or data provided from a plurality of flash memories NVM included in the memory device 6340, or temporarily store meta data of the plurality of flash memories NVM, for example, map data including a mapping table. The buffer memory 6325 may be embodied by volatile memories such as DRAM, SDRAM, DDR SDRAM, LPDDR SDRAM and GRAM or nonvolatile memories such as FRAM, ReRAM, STT-MRAM and PRAM. For convenience of description, FIG. 13 illustrates that the buffer memory 6325 exists in the controller 6320. However, the buffer memory 6325 may exist outside the controller 6320.

The ECC circuit 6322 may calculate an ECC value of data to be programmed to the memory device 6340 during a program operation. The ECC circuit 6322 may perform an error correction operation on data read from the memory device 6340 based on the ECC value during a read operation. The ECC circuit 6322 may perform an error correction operation on data recovered from the memory device 6340 during a failed data recovery operation.

The host interface 6324 may provide an interface function with an external device, for example, the host 6310. The nonvolatile memory interface 6326 may provide an interface function with the memory device 6340 connected through the plurality of channels.

Furthermore, a plurality of SSDs 6300 to which the memory system 110 of FIGS. 1 and 5 is applied may be provided to embody a data processing system, for example, RAID (Redundant Array of Independent Disks) system. At this time, the RAID system may include the plurality of SSDs 6300 and a RAID controller for controlling the plurality of SSDs 6300. When the RAID controller performs a program operation in response to a write command provided from the host 6310, the RAID controller may select one or more memory systems or SSDs 6300 according to a plurality of RAID levels, that is, RAID level information of the write command provided from the host 6310 in the SSDs 6300. The RAID controller may output data corresponding to the write command to the selected SSDs 6300. Furthermore, when the RAID controller performs a read command in response to a read command provided from the host 6310, the RAID controller may select one or more memory systems or SSDs 6300 according to a plurality of RAID levels, that is, RAID level information of the read command provided from the host 6310 in the SSDs 6300. The RAID controller may provide data read from the selected SSDs 6300 to the host 6310.

FIG. 14 is a diagram schematically illustrating another example of the data processing system including the memory system in accordance with the embodiment. FIG. 11 schematically illustrates an embedded Multi-Media Card (eMMC) to which the memory system in accordance with the embodiment is applied.

Referring to FIG. 14, the eMMC 6400 may include a controller 6430 and a memory device 6440 embodied by one or more NAND flash memories. The controller 6430 may correspond to the controller 130 in the memory system 110 of FIGS. 1 and 2. The memory device 6440 may correspond to the memory device 150 in the memory system 110 of FIGS. 1 and 5.

More specifically, the controller 6430 may be connected to the memory device 6440 through a plurality of channels. The controller 6430 may include one or more cores 6432, a host interface 6431 and a memory interface, for example, a NAND interface 6433.

The core 6432 may control overall operations of the eMMC 6400. The host interface 6431 may provide an interface function between the controller 6430 and the host 6410. The NAND interface 6433 may provide an interface function between the memory device 6440 and the controller 6430. For example, the host interface 6431 may serve as a parallel interface, for example, MMC interface as described with reference to FIG. 1. Furthermore, the host interface 6431 may serve as a serial interface, for example, UHS ((Ultra High Speed)-I/UHS-II) interface.

FIGS. 17 to 20 are diagrams schematically illustrating other examples of the data processing system including the memory system in accordance with the embodiment. FIGS. 17 to 20 schematically illustrate UFS (Universal Flash Storage) systems to which the memory system in accordance with the embodiment is applied.

Referring to FIGS. 17 to 20, the UFS systems 6500, 6600, 6700, 6800 may include hosts 6510, 6610, 6710, 6810, UFS devices 6520, 6620, 6720, 6820 and UFS cards 6530, 6630, 6730, 6830, respectively. The hosts 6510, 6610, 6710, 6810 may serve as application processors of wired/wireless electronic devices, particularly mobile electronic devices, the UFS devices 6520, 6620, 6720, 6820 may serve as embedded UFS devices, and the UFS cards 6530, 6630, 6730, 6830 may serve as external embedded UFS devices or removable UFS cards.

The hosts 6510, 6610, 6710, 6810, the UFS devices 6520, 6620, 6720, 6820 and the UFS cards 6530, 6630, 6730, 6830 in the respective UFS systems 6500, 6600, 6700, 6800 may communicate with external devices, for example, wired/wireless electronic devices, particularly mobile electronic devices through UFS protocols, and the UFS devices 6520, 6620, 6720, 6820 and the UFS cards 6530, 6630, 6730, 6830 may be embodied by the memory system 110 illustrated in FIGS. 1 and 5. For example, in the UFS systems 6500, 6600, 6700, 6800, the UFS devices 6520, 6620, 6720, 6820 may be embodied in the form of the data processing system 6200, the SSD 6300 or the eMMC 6400 described with reference to FIGS. 13 to 16, and the UFS cards 6530, 6630, 6730, 6830 may be embodied in the form of the memory card system 6100 described with reference to FIG. 11.

Furthermore, in the UFS systems 6500, 6600, 6700, 6800, the hosts 6510, 6610, 6710, 6810, the UFS devices 6520, 6620, 6720, 6820 and the UFS cards 6530, 6630, 6730, 6830 may communicate with each other through an UFS interface, for example, MIPI M-PHY and MIPI UniPro (Unified Protocol) in MIPI (Mobile Industry Processor Interface). Furthermore, the UFS devices 6520, 6620, 6720, 6820 and the UFS cards 6530, 6630, 6730, 6830 may communicate with each other through various protocols other than the UFS protocol, for example, an UFDs, a MMC, a SD, a mini-SD, and a micro-SD.

In the UFS system 6500 illustrated in FIG. 15, each of the host 6510, the UFS device 6520 and the UFS card 6530 may include UniPro. The host 6510 may perform a switching operation in order to communicate with the UFS device 6520 and the UFS card 6530. In particular, the host 6510 may communicate with the UFS device 6520 or the UFS card 6530 through link layer switching, for example, L3 switching at the UniPro. At this time, the UFS device 6520 and the UFS card 6530 may communicate with each other through link layer switching at the UniPro of the host 6510. In the present embodiment, the configuration in which one UFS device 6520 and one UFS card 6530 are connected to the host 6510 has been exemplified for convenience of description. However, a plurality of UFS devices and UFS cards may be connected in parallel or in the form of a star to the host 6410. The form of a star is a sort of arrangement where a single centralized component is coupled to plural devices for parallel processing. A plurality of UFS cards may be connected in parallel or in the form of a star to the UFS device 6520 or connected in series or in the form of a chain to the UFS device 6520.

In the UFS system 6600 illustrated in FIG. 16, each of the host 6610, the UFS device 6620 and the UFS card 6630 may include UniPro, and the host 6610 may communicate with the UFS device 6620 or the UFS card 6630 through a switching module 6640 performing a switching operation, for example, through the switching module 6640 which performs link layer switching at the UniPro, for example, L3 switching. The UFS device 6620 and the UFS card 6630 may communicate with each other through link layer switching of the switching module 6640 at UniPro. In the present embodiment, the configuration in which one UFS device 6620 and one UFS card 6630 are connected to the switching module 6640 has been exemplified for convenience of description. However, a plurality of UFS devices and UFS cards may be connected in parallel or in the form of a star to the switching module 6640, and a plurality of UFS cards may be connected in series or in the form of a chain to the UFS device 6620.

In the UFS system 6700 illustrated in FIG. 17, each of the host 6710, the UFS device 6720 and the UFS card 6730 may include UniPro, and the host 6710 may communicate with the UFS device 6720 or the UFS card 6730 through a switching module 6740 performing a switching operation, for example, through the switching module 6740 which performs link layer switching at the UniPro, for example, L3 switching. At this time, the UFS device 6720 and the UFS card 6730 may communicate with each other through link layer switching of the switching module 6740 at the UniPro, and the switching module 6740 may be integrated as one module with the UFS device 6720 inside or outside the UFS device 6720. In the present embodiment, the configuration in which one UFS device 6720 and one UFS card 6730 are connected to the switching module 6740 has been exemplified for convenience of description. However, a plurality of modules each including the switching module 6740 and the UFS device 6720 may be connected in parallel or in the form of a star to the host 6710 or connected in series or in the form of a chain to each other. Furthermore, a plurality of UFS cards may be connected in parallel or in the form of a star to the UFS device 6720.

In the UFS system 6800 illustrated in FIG. 18, each of the host 6810, the UFS device 6820 and the UFS card 6830 may include M-PHY and UniPro. The UFS device 6820 may perform a switching operation in order to communicate with the host 6810 and the UFS card 6830. In particular, the UFS device 6820 may communicate with the host 6810 or the UFS card 6830 through a switching operation between the M-PHY and UniPro module for communication with the host 6810 and the M-PHY and UniPro module for communication with the UFS card 6830, for example, through a target ID (Identifier) switching operation. At this time, the host 6810 and the UFS card 6830 may communicate with each other through target ID switching between the M-PHY and UniPro modules of the UFS device 6820. In the present embodiment, the configuration in which one UFS device 6820 is connected to the host 6810 and one UFS card 6830 is connected to the UFS device 6820 has been exemplified for convenience of description. However, a plurality of UFS devices may be connected in parallel or in the form of a star to the host 6810, or connected in series or in the form of a chain to the host 6810, and a plurality of UFS cards may be connected in parallel or in the form of a star to the UFS device 6820, or connected in series or in the form of a chain to the UFS device 6820.

FIG. 19 is a diagram schematically illustrating another example of the data processing system including the memory system in accordance with an embodiment of the present invention. FIG. 19 is a diagram schematically illustrating a user system to which the memory system in accordance with the embodiment is applied.

Referring to FIG. 19, the user system 6900 may include an application processor 6930, a memory module 6920, a network module 6940, a storage module 6950 and a user interface 6910.

More specifically, the application processor 6930 may drive components included in the user system 6900, for example, an OS, and include controllers, interfaces and a graphic engine which control the components included in the user system 6900. The application processor 6930 may be provided as System-on-Chip (SoC).

The memory module 6920 may be used as a main memory, work memory, buffer memory or cache memory of the user system 6900. The memory module 6920 may include a volatile RAM such as DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, LPDDR SDARM, LPDDR3 SDRAM or LPDDR3 SDRAM or a nonvolatile RAM such as PRAM, ReRAM, MRAM or FRAM, For example, the application processor 6930 and the memory module 6920 may be packaged and mounted, based on POP (Package on Package).

The network module 6940 may communicate with external devices. For example, the network module 6940 may not only support wired communication, but also support various wireless communication protocols such as code division multiple access (CDMA), global system for mobile communication (GSM), wideband CDMA (WCDMA), CDMA-2000, time division multiple access (TDMA), long term evolution (LTE), worldwide interoperability for microwave access (Wimax), wireless local area network (WLAN), ultra-wideband (UWB), Bluetooth, wireless display (WI-DI), thereby communicating with wired/wireless electronic devices, particularly mobile electronic devices. Therefore, the memory system and the data processing system, in accordance with an embodiment of the present invention, can be applied to wired/wireless electronic devices. The network module 6940 may be included in the application processor 6930.

The storage module 6950 may store data, for example, data received from the application processor 6930, and then may transmit the stored data to the application processor 6930. The storage module 6950 may be embodied by a nonvolatile semiconductor memory device such as a phase-change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (ReRAM), a NAND flash, a NOR flash and a 3D NAND flash, and provided as a removable storage medium such as a memory card or external drive of the user system 6900. The storage module 6950 may correspond to the memory system 110 described with reference to FIGS. 1 and 5. Furthermore, the storage module 6950 may be embodied as an SSD, an eMMC and an UFS as described above with reference to FIGS. 15 to 20.

The user interface 6910 may include interfaces for inputting data or commands to the application processor 6930 or outputting data to an external device. For example, the user interface 6910 may include user input interfaces such as a keyboard, a keypad, a button, a touch panel, a touch screen, a touch pad, a touch ball, a camera, a microphone, a gyroscope sensor, a vibration sensor and a piezoelectric element, and user output interfaces such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display device, an active matrix OLED (AMOLED) display device, an LED, a speaker and a motor.

Furthermore, when the memory system 110 of FIGS. 1 and 5 is applied to a mobile electronic device of the user system 6900, the application processor 6930 may control overall operations of the mobile electronic device. The network module 6940 may serve as a communication module for controlling wired/wireless communication with an external device. The user interface 6910 may display data processed by the processor 6930 on a display/touch module of the mobile electronic device. Further, the user interface 6910 may support a function of receiving data from the touch panel.

In accordance with embodiments described above, it is advantageous that the memory system can attempt to recover data in a state in which the risk of loss of data is reduced at the point of time when external factors are later removed, after an operation for moving or programming the large amount of data has not been completed due to the external factors such as a power supply interruption.

Further, the disclosure can provide an apparatus and a method for improving operation stability and reliability in a memory system capable of handling a large amount of data.

While the disclosure has been described with respect to the specific embodiments, it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims. 

What is claimed is:
 1. A memory system comprising: a memory device including plural memory blocks each including plural pages storing data; and a controller suitable for loading data from first memory blocks among the plural memory blocks to perform command operations corresponding to plural commands, and securing second memory blocks among the plural memory blocks to store data updated by the command operations, wherein the controller excludes the first memory blocks from the second memory blocks.
 2. The memory system according to claim 1, wherein the controller excludes the first memory blocks from the second memory blocks even if the first memory blocks become a free block during the command operations, and wherein the controller includes, after the command operations are completed, the first memory blocks, which become the free block during the command operations, in the second memory blocks.
 3. The memory system according to claim 1, wherein the controller generates and manages a free block list having a bitmap including bit information indicating whether each of the first memory blocks, which become a free block during the command operations, and the second memory blocks are available.
 4. The memory system according to claim 3, wherein the controller determines, in the free block list, that first bit information corresponding to the first memory blocks, which become a free block during the command operations, has a first value and second bit information corresponding to the second memory blocks has a second value.
 5. The memory system according to claim 1, wherein the controller generates a list regarding the second memory blocks before the command operations are begun, and then the list is not updated nor changed while the command operations are performed.
 6. The memory system according to claim 1, wherein the controller updates, while the command operations are performed, a list when at least one of memory blocks other than the first memory blocks is changed to the second memory blocks.
 7. The memory system according to claim 1, wherein the controller updates a list regarding newly added second memory blocks regardless of the command operations, and the list includes bit information each indicating whether each of the second memory blocks is available.
 8. The memory system according to claim 1, wherein the controller loads, after storing information regarding the command operations to the second memory blocks and before an occurrence of sudden power off (SPO), the information stored in the second memory blocks to perform the command operations when a power is supplied.
 9. The memory system according to claim 1, wherein the command operations include a foreground operation and a background operation performed in the memory device, and wherein the foreground operation and the background operation include a data program operation, a data erase operation or a data read operation.
 10. A memory system comprising: a memory device including a plurality of memory blocks each including a plurality of pages in which data is stored; and a controller suitable for loading map data and user data for an operation corresponding to a command on first memory blocks in the plurality of memory blocks, and determining second memory blocks which store updated map data and updated user data through the operation corresponding to the command, wherein the controller excludes, even if at least one of the first memory blocks becomes a free block, the at least one first memory block from the second memory blocks until the updated map data and the updated user data are stored in the second memory blocks.
 11. The memory system according to claim 10, wherein the controller generates a list regarding the second memory blocks before the command operations are begun, and then the list is not updated nor changed while the command operations are performed.
 12. The memory system according to claim 10, wherein the controller updates, while the command operations are performed, a list when at least one of memory blocks other than the first memory blocks is changed to the second memory blocks.
 13. The memory system according to claim 10, wherein the controller updates a list regarding newly added second memory blocks regardless of the command operations, and the list includes bit information indicating whether each of the second memory blocks is available.
 14. The memory system according to claim 10, wherein the command operations include a foreground operation and a background operation performed in the memory device, and wherein the foreground operation and the background operation include a data program operation, a data erase operation or a data read operation.
 15. A method for operating a memory system, the method comprising: receiving plural commands entered from a host and associated with a memory device including plural memory blocks each including plural pages storing data; loading data from first memory blocks among the plural memory blocks to perform command operations corresponding to the plural commands; and securing second memory blocks among the plural memory blocks to store data updated through the command operations, wherein the controller excludes, even if at least one of the first memory blocks becomes a free block, the at least one first memory block from the second memory blocks until the updated data is stored in the second memory blocks.
 16. The method according to claim 15, wherein the securing of the second memory blocks includes generating a list in which information of the second memory blocks are arranged and sorted.
 17. The method according to claim 16, wherein the list includes bit information corresponding to each memory block and indicating whether each of the first memory blocks, which become a free block during the command operations, and the second memory blocks are available.
 18. The method according to claim 17, wherein the controller updates the list when a new free block is generated, regardless of the command operations.
 19. The method according to claim 16, wherein the list is generated before the command operations are begun, and the list is not updated nor changed while the command operations are performed.
 20. The method according to claim 16, wherein the securing of the second memory blocks further includes updating a list when at least one of memory blocks other than the first memory blocks is changed to the second memory blocks while the command operations are performed. 